
Hi,

                     *** UPGRADING FROM VERSIONS < 0.90 ***


with version 0.90 I've changed the concept of CheckFATT. This was mainly done
because the "old" solution was a bit stupid, I have to admit :-)


  CheckFATT     [Adjust] [Notify] [PutOnHold | MoveBad] [MoveOwn <{dir}>]

                  [...]

                  Notify       Notify source & destination about the stopped
                               FileAttach.

                  PutOnHold    Put the file on hold for the destination. This
                               includes "Notify", so don't set them both.

                  MoveBad      Move the FATT-file to MM's #BADDIR.

                  You can set PutOnHold *OR* MoveBad. If you  don't set one of
                  these two keywords, the file will simply be deleted.

                  MoveOwn      If this is enabled,  MM_StarTrack will move all
                   {dir}       files for  you to the  specified  directory, so
                               that you can  use your  #MAILAREA-(alt-)path as
                               spool-dir for routed files.



The difference now is that I've, exchanged the #MAILAREA-(alt-)path with the
MoveOwn-path (former PutOnHold-path). If you want to use this new feature, in
MM.cfg, you have to set the #MAILAREA-AltPath to the path the FATTs should be
kept (e.g. Out:FileAttachs/) and the MoveOwn-path to the one you've used as
#MAILAREA-AltPath until now. Hope you could follow me :-)


This methode has the big andvantage, that MM will no longer have problems with
the FATT's and files for others will be seperated from files for you.





                      *** UPGRADING FROM VERSION 0.90 ***


Since v0.95 the REMAP-routines are *COMPLETLY* rewritten! Now it is *MUCH* more
powerful than before!

The old cfg is NOT longer compatible with the new one, but I've also included a
script to convert your cfg. Just start it and all will be done for you.




  5.10 #REMAP(FROM|TO) - Remapping msgs and/or users
  --------------------------------------------------

   Here you can remap msgs. But be careful! This is a very powerful function, so
   read this part *VERY* *CAREFULLY*!!!


   IMPORTANT NOTE: If you upgrade from a MM_StarTrack-version <0.95, you have to
                   "rx MM_ST_ConvertCfg" because there is a *MAJOR* change up to
                   version >=0.95!!!


   #REMAP(FROM|TO)

   Address  OLD,NEW   OLD  The old from/to-address
                      NEW  The new from/to-address

   Name     OLD,NEW   OLD  The old from/to-name
                      NEW  The new from/to-name

   AddInfo            Add the file Text.Remap{Src|Dst} at the top of the msg.

   Reply              ONLY valid for #REMAPTO!


   You need not use  all these fields. In general, this function  can be divided
   into five parts:

    1. Remap only the name, not depending on the  address. In this  case, do not
       use an 'Address'-statement.

    2. Remap only  the address, not depending  on the name. In this case, do not
       use a 'Name'-statement.

    3. Remap the name depending on the address. In this case, 'Addr OLD' & 'Name
       OLD,NEW' must be set.

    4. Remap  a name to  multiple new  addresses, depending on  the domain. This
       means, check the name  and if it matches, use that new address, where the
       domains are matching. In  this case, you must  set at least  'Name OLD' &
       'Address NEW', where NEW can be '"<addr> [addr] [...]"'. You must not use
       'Address OLD' in this case but you  can use 'Name NEW' to remap the name,
       too.

    5. Remap address & name  to a new address  & name. In  this case  all fields
       have to be used.


   You can use wildcards nearly  *EVERYWHERE*! E.g. you  can remap all msgs from
   "Robert Ho(f|ff)man(n|nn)" to "Robert Hofmann" etc...

   You have to use  5D-addresses only. The  new address may  also contain simple
   wildcards. To make  sure that you use working wildcards, please check  it out
   with  MM_ST_CheckWildcard.rexx  which  you  can  find  in the  rexx-drawer of
   MM_Startrack  (see also 5.10.1). This is  only neccessary if  the new address
   also contains a wildcard.

   The new dest.addr. has to exist or  listed in your #NODEs,  otherwise it will
   be bounced.






If you have any problems, just let me know :-)







  _  o         Robert Hofmann         2:2490/1015@FidoNet   37:108/220@TrekNet
 |<)_/#                              39:171/101@AmigaNet   107:1805/230@TrekNet
 TT  <T  robert@next.amistep.osn.de  56:63/201@XNet        213:314/9127@XCessNet

